Backport of NET-11798: Set APIGateway TLSConfig if unset or empty into release/1.20.x #22076
+639
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #21984 to be assessed for backporting due to the inclusion of the label backport/1.20.
🚨
The person who merged in the original PR is:
@NiniOak
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.
The below text is copied from the body of the original PR.
Description
The API Gateway TLS.{Min,Max}Versions and TLS.CipherSuites settings are not applied to API Gateway Listeners. To fix this:
setAPIGatewayTLSConfig
that handles the logic for setting TLS configuration for APIGatewayTesting & Reproduction steps
Tested manually, as follows:
Using this config file
config.hcl
make dev-build
consul agent -dev -config-file consul.hcl
consul connect envoy -gateway api -service my-gateway -register
curl -s 0:19000/config_dump | grep tls_minimum
"tls_minimum_protocol_version": "TLSv1_3"
Links
PR Checklist
Overview of commits